There are two types of output logs: the log for SuperMap iDesktopX and the log for SuperMap iObjects, which record the information output by the desktop and components respectively. The content of the logs includes output info from the program's output window, exception information, etc. The logs are stored in the "log" folder under the "bin" directory in the root directory.

　　#!/bin/bash 　　export ORACLE_HOME=/opt/oracleClient (Path to the client) 　　export PATH=$PATH:$ORACLE_HOME 　　export LD_LIBRARY_PATH=$ORACLE_HOME:$LD_LIBRARY_PATH

After the Oracle client environment variable is set, restart SuperMap iDesktopX in this Terminal, and the Oracle data source can be used normally. Creating or connecting to an Oracle data source requires configuring the Oracle client in the environment where the desktop is running, adding the client to LD_LIBRARY_PATH. A profile example can be provided, and tnsnames.ora needs to be configured; if connecting via the EZConnect method, tnsnames may not need to be configured.

The source code in the develop branch depends on iObjects Java that is still under development and unreleased. Users cannot obtain the newest version of iObjects, which leads to compilation errors. It is recommended that users fetch the source code of a fixed version from the Tags and simultaneously download the corresponding iObjects Java version from the SuperMap official website for compilation.

There are three reasons for this situation: first, the license is not configured; second, the license configuration was not successful; third, the license has expired. For the first two reasons, the solution is to reconfigure the license. The configuration methods for Windows and Linux operating systems differ. Please refer to the license configuration sections in Windows Configuration Guide and Linux Configuration Guide for specific operations.

On SUSE, it's necessary to install third-party database clients to correctly load sdx data engines. Failure to load one sdx can affect the loading of other sdx data engines, leading to the inability to open any data source or program startup failure. The sdx data engine files that require third-party database clients are: libSuEngineSRDB.sdx, libSuEngineOracle.sdx, libSuEngineDMCI.sdx, libSuEngineOsp.sdx, libSuEngineAltibase.sdx, libSuEngineDB2.sdx, libSuEngineKDB.sdx. For example: If you need to use an Oracle data source, first install the Oracle client, then delete all the *.sdx files listed above except libSuEngineOracle.sdx, and then start SuperMap iDesktopX. Similarly, if other database engines are needed, perform corresponding processing.

The solution is: Keep libSuEngineImagePlugin.sdx and the required database engine files in the bin directory of the product package, and delete the unnecessary database engine files (*.sdx from the list above).

The code on git is divided into two branches: master and develop. The master branch is the main version branch, and stable releases are pushed to the master branch. The develop branch is the development branch where daily code modifications are pushed, but code stability is not guaranteed. Therefore, the develop version may encounter situations where exceptions are thrown.

This is caused by missing Chinese fonts in the Linux system. Place a Chinese font in the jre/jre/lib/fonts folder under the product package directory, and the program interface text will display normally.

During map visualization, some special fonts are used, such as "microsoft yahei", etc. These fonts may not be available in the Linux operating system, leading to display exceptions for map annotations and other text features. Please check the attachments fonts_1.zip and fonts_2.zip, which contain mainstream common fonts. When using this program or source code on a Linux operating system, please download and extract them to the "root directory/support/fonts/" directory (create it if it doesn't exist), and add the environment variable SUPERMAP_ROOT, setting its value to "root directory/support/". Then, refer to "SuperMap iDesktopX 8C Extension Development Guide.doc" for environment configuration, and text features will display normally.

If the Linux system lacks a Chinese locale, it is recommended to change the published map name to an English name; or publish the map service containing a Chinese name on a Linux system that has a Chinese locale.

Copy the "libstdc++.so.6" file from the support folder in the desktop package to the Bin directory of the components to resolve this issue.

The startup of the desktop relies on graphical interface libraries and can only be launched and operated graphically on a GUI. Therefore, it is first necessary to ensure that the remote server is configured with a graphical interface library. Secondly, choose a visual remote connection tool, as SecureCRT is a command-line remote connection tool. It is recommended to switch to another remote control tool, such as vnc or xmanager. Both tools can remotely connect to UNIX or Linux and perform graphical operations, but they require corresponding configuration. For VNC configuration, please refer to How to configure vnc on centos 5.5 and Installation and Configuration of VNC.

Notes: If encountering this issue on other Linux operating systems, the same solution can be adopted.

Executing functions like modifying color schemes or saving layouts to the template library writes data to the installation path. When starting idesktopx by directly double-clicking SuperMap iDesktopX.exe, there is no permission to write data to the system directory, causing the functions to fail. Running SuperMap iDesktopX.exe as an administrator can resolve the above problem.

When starting idesktopx by directly double-clicking SuperMap iDesktopX.exe, there is no permission to read/write data in system directories. This issue can be resolved in the following ways:

• Place the data to be used in a non-system directory and change the output file path to a non-system directory; (Recommended)
• Right-click on SuperMap iDesktopX.exe, select "Run as administrator";
• Right-click on SuperMap iDesktopX.exe, select "Properties", change the .exe permission to administrator, and rerun the .exe;

This situation is due to missing the Microsoft Visual C++ runtime environment. In the product package installation path\SuperMap\SuperMap iDesktopX\support folder, double-click vcredist110_x64.exe. After successfully installing Microsoft Visual C++ 2012, it can start normally.

On a Windows Server system, starting SuperMap iDesktopX prompts the error shown in the figure below. How to solve this?

This is caused by a DLL file failing to load. It can be resolved by the following methods:

1. Restart SuperMap iDesktopX;
2. If restarting still reports the same error, open the SuperMap.Desktop.Parameter.xml file in the product package\configuration folder, change the true in "<loadDll loadDll="true"/>" to False;
3. After modification, start SuperMap iDesktopX again.

Starting SuperMap iDesktopX depends on a jre 1.7 or newer environment. Because the jre version does not meet the requirement, Java fails to start. The solutions are as follows:

• Uninstall the locally installed old jre environment, install jre 1.7 or newer, and then restart Java;
• The Java product package comes with a jre 1.7 environment. When starting idesktopx, it prioritizes the locally configured environment, leading to startup failure. If users do not want to uninstall the local jre environment, they can modify the startup.sh script by moving "$JRE_PATH:" in "export PATH=$SUPERMAP_ROOT:$LD_LIBRARY_PATH:$JRE_PATH:$PATH" to the very front, i.e.: export PATH=$JRE_PATH:$SUPERMAP_ROOT:$LD_LIBRARY_PATH:$PATH. Re-execute the startup.sh file to start Java.

Notes: This issue has been resolved in version 9D, and the problem of being unable to start due to a low jre environment will not occur.

Using a Tongxin machine, the GPA modeling canvas cannot be browsed, and the following information is displayed in the console:

Execute the following command in the console:xhost +SI:localuser:root

The GPA modeling canvas displays for a while and then crashes, and the console displays the following information:

After starting the software, the UI displays exception. Possibly as shown below: